.github/workflows/test.yml:209

• The job expects a scikit-build-core Coverage build tree (build/editable/Coverage) later (gcovr + ctest), but the install step runs uv sync without selecting Coverage build type. Unless an undocumented env var happens to be honored, build/editable/Coverage won’t exist and the subsequent steps will fail.

      - name: Install package
        run: |
          uv sync --no-progress --group test --all-extras -v

.github/workflows/test.yml:266

• SKBUILD_CMAKE_DEFINE is not the documented mechanism for passing CMake definitions to scikit-build-core in this repo; use SKBUILD_CMAKE_ARGS (or pass --config-settings=cmake.define... to uv sync) so MPI is reliably enabled for Sonar’s compilation database.

    env:
      SKBUILD_CMAKE_DEFINE: "monoprop_ENABLE_MPI=ON"

.github/workflows/test.yml:176

• Codecov’s files: input is typically parsed as a comma-separated list; the second entry here has a leading space, which can be interpreted as part of the filename and cause the ctest report upload to be skipped.

      - name: Upload test results to Codecov
        uses: codecov/codecov-action@v7.0.0
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          files: pytest-${{ steps.test-group-label.outputs.label }}.xml, ctest-${{ steps.test-group-label.outputs.label }}.xml
          report_type: test_results

CMakeLists.txt:8

• This project now relies on scikit-build-core-only configuration, but the current direct-CMake path only emits a warning and then continues into SKBUILD-specific code paths (which can fail later with less actionable errors). If direct CMake invocation is intentionally unsupported, prefer failing fast here.

if(NOT SKBUILD)
  message(
    WARNING
    "\

.github/workflows/test.yml:60

• SKBUILD_CMAKE_DEFINE is not the documented knob for scikit-build-core in this repo (docs use SKBUILD_CMAKE_ARGS / --config-settings=cmake.define...). If this env var is ignored, the matrix ‘wide term index’ build won’t actually be wide.

This issue also appears in the following locations of the same file:

• line 171
• line 206
• line 265

    env:
      SKBUILD_CMAKE_DEFINE: "monoprop_WIDE_TERM_INDEX=${{ matrix.wide }}"

.github/workflows/docpages.yml:44

• SKBUILD_CMAKE_DEFINE is not the documented knob for scikit-build-core in this repo. If it’s ignored, the docs build will still compile the C++ unit tests even though this workflow intends to disable them.

    env:
      SKBUILD_CMAKE_DEFINE: monoprop_ENABLE_CXX_UNIT_TESTS=OFF

justfile:49

• The repo docs still reference the old Just recipes (test-py, test-py-mpi, test-py-mpi-matrix) that were removed/renamed here (see docs/content/docs/testing.mdx:18,26-27). This makes the documented test commands incorrect after this change.

test:
    uv run python -m pytest -m "not mpi"
    ctest --test-dir build/editable/Release --output-on-failure

# MPI is off by default in source builds, so build an MPI-enabled editable install
# first, then run the suite under mpiexec with --no-sync (avoids a per-rank resync).
# Pass RANKS as either a single integer or a semicolon-separated list (e.g. "1;2;4").

test-mpi RANKS='':
    export OMPI_MCA_rmaps_base_oversubscribe="1"
    uv sync --all-extras --group test --reinstall-package monoprop --no-cache --config-settings-package="monoprop:cmake.define.monoprop_ENABLE_MPI=ON" -v
    ranks="${1:-${monoprop_MPI_TEST_PROCS:-2}}"
    for r in ${ranks//;/ }; \
    do echo "Running full Python test suite with ${r} MPI rank(s)"; \
    mpiexec -n "$r" uv run --no-sync python -m pytest tests --with-mpi -v; \
    echo "Running C++ unit tests with ${r} MPI rank(s)"; \
    ctest --test-dir build/editable/Release --output-on-failure \
    done

CMakeLists.txt:32

• include/monoprop/Info.h is generated from include/monoprop/Info.h.in, but the placeholders @PROJECT_VERSION_FULL@ and @GIT_COMMIT@ are no longer defined anywhere in CMake (DynamicVersion was removed). As a result, monoprop::version() and monoprop::git_commit() will expand to empty strings in the built artifact.

endif()

if(APPLE)